home *** CD-ROM | disk | FTP | other *** search
- In article <SCOLLORA.88.2DA0712F@lmumail.lmu.edu> SCOLLORA@lmumail.lmu.edu (Sal Collora) writes:
- >Subject: LWP and Gopher
- >From: SCOLLORA@lmumail.lmu.edu (Sal Collora)
- >Date: Mon, 4 Apr 1994 13:00:39
-
- >Hello all...
-
- >We here at LMU are having a funny problem. It seems as though when using LWP
- >for DOS (under Windows) we cannot Gopher to "gopher.tc.umn.edu". It just sits
- >and tries to connect.
-
- >When I try using Peter Tattam's Trupmet Winsock Stack everything works fine.
- >Have I found a bug in WINSOCK.DLL or WLIBSOCK.DLL from Novell, or am I just
- >going crazy.
-
- >I wouldn't usually make a big deal about it, but there are many users here who
- >access that site to get to the European and Asian gopher server list. I also
- >tried finding a Gopher client native to the LWP TCP/IP stack but was
- >unsuccessful. The one I did find was a port of the Unix client and it didn't
- >even recognize the DNS, so I couldn't gopher anywhere.
-
- >I am trying to find some reason to keep Lan Workplace around. Can someone
- >please give me one??
-
- >Frustrated as hell...
-
- >..Sal
- >*************************************************************
- >*Salvatore Collora System Administrator*
- >*Loyola Marymount University Network Consultant *
- >*Phone 310-338-7719 Fax 310-338-7717 *
- >*************************************************************
-
-
- I just started using LWP's TCP/IP stack, which now comes bundled with
- NWRequester 1.1 (?). After reading your post, I tried using Mosaic to get to
- UMN's gopher site. It would not connect. I tried the same thing on a machine
- in the next office, using Trumpet Winsock. It worked. When I tried
- Telnetting to gopher.tc.umn.edu, using LWP's TCP/Ip, the IP address it tried
- was 0.134.84.132. When I tried Telnetting to gopher.tc.umn.edu, using a
- telnet under Trumpet Winsock, the IP address it tried was 134.84.132.9. I
- have no idea why this is happening. I would not have discovered it except for
- your post. If anyone has any ideas (or especially solutions!) please respond.
- I wonder if any other sites can't be reached?
-
- I will refrain from making the obvious derogatory remarks about Novell's
- abilities to write code. I'll also refrain from mentioning how Novell's
- products ALWAYS have this kind of nasty surprise. Perhaps this problem is not
- their fault.
-
- Kerry Moorman
- Moorman@WKYUVM.WKU.EDU
-
-